> production <<- list(…)
Using in R in a non-interactive way:
- R scripts are scheduled to run without manual intervention (eg CRON or upstream job trigger, API request)
- need for a standard, eg containerized environment (eg R and package versions, OS packages,
.Rprofile etc)
- security! (safeguarded production environment, SQL injection, AppArmor, encrypted credentials etc)
- the output of the jobs are recorded and monitored (eg
error handler for ErrBit, CloudWatch logs or Splunk etc), alerts and notifications
- if an error occurs, usually there is no other way to figure out what happened then looking at the recorded job output, so better log than sorry